Cooperatively Managing Enforcement of Energy Related Policies Between Virtual Machine and Application Runtime

ABSTRACT

A mechanism is provided in a data processing system for runtime based enforcement of energy policies collaboratively. The application runtime environment executing within a virtual machine on the data processing system receives notification of a change in energy policy for the virtual machine or the physical host it is running on. Responsive to determining the virtual machine is to be run under a power cap based on the notification of a change in energy policy, the application runtime environment dynamically modifies execution of an application in the application runtime environment or requests the execution environment for delaying enforcement of energy policies. The application comprises a set of application modules.

BACKGROUND

The present application relates generally to an improved data processing apparatus and method and more specifically to mechanisms for runtime based enforcement of energy related policies between a host or virtual machine and an application runtime in a cloud computing environment.

Cloud computing is the use of computing resources (hardware and software) that are delivered as a service over a network (typically the Internet). Cloud computing entrusts remote services with a user's data, software and computation. Using software as a service, users also rent application software and databases. The cloud providers manage the infrastructure and platforms on which the applications run. End users may access cloud-based applications through a web browser or a light-weight desktop or mobile app while the business software and user data are stored on servers at a remote location.

In the software-as-a-service (SaaS) model, cloud providers install and operate application software in the cloud, and cloud users access the software from cloud clients. The cloud users do not manage the cloud infrastructure and platform on which the application is running. This eliminates the need to install and run the application on the cloud user's own computers, simplifying maintenance and support. What makes a cloud application different from other applications is its elasticity. This can be achieved by cloning tasks onto multiple virtual machines at run-time to meet the changing work demand. Load balancers distribute the work over a set of virtual machines. This process is inconspicuous to the cloud user who sees only a single access point.

An application runtime system or runtime environment is a software component designed to support the execution of computer applications written in some computer language. The application runtime contains implementations of basic low-level commands and may also implement higher-level commands and may support type checking, debugging, and even code generation and optimization.

An application runtime relieves programmers from the burden of writing code for mundane tasks, such as drawing text on the screen or making an Internet connection. It also provides an abstraction layer that hides the complexity or variations in the services offered by the operating system.

SUMMARY

In one illustrative embodiment, a method, in a data processing system, is provided for runtime based enforcement of energy policies. The method comprises receiving, by an application runtime environment executing within a virtual machine on the data processing system, notification of a change in energy policy for the virtual machine or the physical host system on which the virtual machine is executing. The method further comprises responsive to determining the virtual machine is to be run under a power cap based on the notification of a change in energy policy, dynamically modifying, by the application runtime environment, execution of an application in the application runtime environment. The application comprises a set of application modules.

In other illustrative embodiments, a computer program product comprising a computer useable or readable medium having a computer readable program is provided. The computer readable program, when executed on a computing device, causes the computing device to perform various ones of, and combinations of, the operations outlined above with regard to the method illustrative embodiment.

In yet another illustrative embodiment, a system/apparatus is provided. The system/apparatus may comprise one or more processors and a memory coupled to the one or more processors. The memory may comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform various ones of, and combinations of, the operations outlined above with regard to the method illustrative embodiment.

These and other features and advantages of the present invention will be described in, or will become apparent to those of ordinary skill in the art in view of, the following detailed description of the example embodiments of the present invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The invention, as well as a preferred mode of use and further objectives and advantages thereof, will best be understood by reference to the following detailed description of illustrative embodiments when read in conjunction with the accompanying drawings, wherein:

FIG. 1 depicts a cloud computing node according to an illustrative embodiment;

FIG. 2 depicts a cloud computing environment according an illustrative embodiment;

FIG. 3 depicts abstraction model layers according to an illustrative embodiment;

FIG. 4 is a block diagram of a data processing system with application runtime based enforcement of energy policies in accordance with an illustrative embodiment; and

FIGS. 5A and 5B present a flowchart illustrating operation of a mechanism for application runtime based enforcement of energy policies in accordance with an illustrative embodiment.

DETAILED DESCRIPTION

The illustrative embodiments provide a mechanism for runtime based enforcement of energy policies in a cloud computing environment. The application runtime is notified of host power policies and any changes in power policies either as an external input or higher-level cloud/datacenter policies or due to migration of a virtual machine on other hosts or pools where power policies are different. When the application runtime running inside the virtual machine finds out that the host it is running on is executing under a power cap, the application re-prioritizes running of some modules and services, especially modules running batch jobs or jobs that are typically processor or memory intensive, i.e., power intensive. Dynamically adaptive behavior of the application in accordance with the illustrative embodiments, as per the power constraints in the execution environment, helps the application maintain its power usage within set limits without compromising much on its SLA and responsiveness, hence helping meet power limits in the cloud environment with minimal overheads to the cloud provider and cloud customers. This can also enable applications to tide through some predictable (known through historic trends) peaks and resource consumption surges in the cloud environment.

Furthermore, the host can also provide information to the virtual machine on the time when a power cap will be actuated. The application runtime executing in the virtual machine, on being notified of the power cap event, may inform the host system about the time remaining to finish some high priority work, such as serving a high priority request or executing a transaction guaranteed to be atomic. If the time remaining for finishing the job is not significantly higher than the time at which the power cap will be enforced, the application runtime may communicate this information to the host, which may determine whether to delay enforcing the power cap.

Each application module may have an attribute that indicates whether the module is sensitive to power capping or aggressive power saving mode. The application runtime, before loading the application modules, may check the attribute and compare it with the power policy of the host. Based on the attribute value, the application runtime can load the module or disable its loading. Additionally, if the application runtime decides to not load a given application module based on its attribute value, the application runtime may query a service registry to get a version of the module with specific functionality suitable for the power policy, if available. The application runtime may also query a trusted module object registry to deploy application modules that provide needed functionality with power efficiency or high performance, for example, as per the changes in the power policy. If the runtime has already loaded a power/performance sensitive module and the power policies have changed, it may suspend or disable such module in order to meet the power limit requirements and still maintain it's SLA.

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computing node is shown. Cloud computing node 10 is only one example of a suitable cloud computing node and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention described herein. Regardless, cloud computing node 10 is capable of being implemented and/or performing any of the functionality set forth hereinabove,

In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and no on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10 is shown in the form of a general-purpose computing device. The components of computer system/server 12 may include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein. Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g. network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 2 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 2) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 3 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes, in one example IBM® zSeries® systems; RISC (Reduced Instruction Set Computer) architecture based servers, in one example IBM pSeries® systems; IBM xSeries® systems; IBM BladeCenter® systems; storage devices; networks and networking components. Examples of software components include network application server software, in one example IBM WebSphere® application server software; and database software, in one example IBM DB2® database software, (IBM, zSeries, pSeries, xSeries, BladeCenter, WebSphere, and DB2 are trademarks of International Business Machines Corporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers; virtual storage; virtual networks, including virtual private networks; virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions described below. Resource provisioning provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal provides access to the cloud computing environment for consumers and system administrators. Service level management provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 66 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation; software development and lifecycle management; virtual classroom education delivery; data analytics processing; and transaction processing.

Open Services Gateway Initiative (OSGi™) framework is a module system and service platform for the Java™ programming language that implements a complete and dynamic component model. The OSGi™ framework installs units of resources called “bundles,” which are application modules that together make up an application. Applications or bundles can be remotely installed, started, stopped, updated, and uninstalled without requiring a reboot; management of Java™ packages/classes is specified in great detail. Application life cycle management (start, stop, install, etc.) is done via application programming interfaces (APIs) that allow for remote downloading of management policies. The service registry allows bundles to detect the addition of new services, or the removal of services, and adapt accordingly.

Bundles can export services or run processes and have their dependencies managed, such that a bundle can be expected to have its requirements managed by the container (runtime environment). Each bundle can also have its own internal classpath, so that it can serve as an independent unit, should that be desirable. All of this is standard such that any valid OSGi™ bundle can theoretically be installed in any valid OSGi™ container.

In a cloud environment, there may be situations where a specific resource pool can run under a power cap. In such situations, it may be desirable to have the application be aware of power policy information and to adapt its behavior as per the prevailing power conditions. This may reduce application errors or inconsistency in application performance, thereby maintaining the responsiveness and stability of the overall application and the cloud environment as a whole.

As described above, management layer 64 provides functions of resource provisioning, service level management, security, and so forth. Thus, management layer 64 may provision resources to a virtual machine and an application runtime executing within the virtual machine. Management layer 64 may also migrate a virtual machine to another host or modify power policies of underlying host resources. In accordance with an illustrative embodiment, the application runtime is made aware of power policies of the execution environment (host or virtual machine) and based on the inputs and notifications from the execution environment, respond back or adapt applications to comply with power policies, still maintaining the desired behavior and responsiveness of applications.

FIG. 4 is a block diagram of a data processing system with application runtime based enforcement of energy policies in accordance with an illustrative embodiment. Data processing system 400 comprises host 450 having hardware resources, such as processors, memory, I/O devices, persistent storage devices, etc. Host 450 runs virtual machine monitor (VMM) 440, which virtualizes hardware resources of host 450 to be allocated to virtual machines 431, 432, 433. A virtual machine (VM) is a software implementation of a machine (i.e., a computer) that executes programs like a physical machine. A system virtual machine provides a complete system platform which supports the execution of a complete operating system (OS). VMs may emulate an existing architecture, and are built with the purpose of providing a platform to run programs where having multiple instances of virtual machines lead to more efficient use of computing resource, both in terms of energy consumption as well as cost effectiveness (known as hardware virtualization, the key to cloud computing environment).

VM 1 431 runs application runtime 410, which loads application 411 made up of application modules 412. In accordance with the illustrative embodiment, application runtime 410 gets a notification of power policies from VM 1 431, VMM 440, or host 450. The notification may identify host or virtual machine power management policy (e.g., whether it is in power saving mode or performance mode). The notification may identify changes being made to the power management policy. The notification may identify that the power policy is being changed from performance mode to power saving mode or vice versa. The notification may identify that power capping is being enforced and the time duration left for power capping to become effective. The notification may identify that power capping is to be removed and the time duration left for power capping to be removed. The notification may identify scheduled or periodic changes to power management policy like power savings mode or power capping enforcement or removal.

Based on the notification, application runtime 410 may check attributes of application modules 412. The attributes may be specified as metadata of the modules or the service registration attributes of the associated service by the provider module. Application runtime 410 determines whether application modules 412 are sensitive to power capping or aggressive power saving mode, such as computation or memory intensive tasks.

For modules that are sensitive to power policy, the application runtime 410 may make decisions regarding the behavior of application 411. Application runtime 410 may request the execution environment to defer actuation of the power management policy until execution of critical workload or critical transaction in the workload is complete.

Application runtime 410 may seek out power-conservative alternate implementation of services and functionalities, which may compromise on performance, still maintaining the consistency of functionality in the application. The application runtime 410 may contact trusted module registry 420 to dynamically provision alternate modules that satisfy the power restrictions of the policy or power cap. One way to implement these power-conservative modules is to have modules with fewer concurrent threads and better memory management.

When power capping is going to be revoked or power management policy changed from power saving to performance mode, application runtime 410 may request high performance, power-intensive alternate implementations of currently deployed services and functionality (modules). One way to implement these high-performance modules is to have multiple parallel execution paths (threads) in these modules.

In order to meet the power constraints due to the execution environment's power management policy enforcement, the application runtime 410 may temporarily disable sensitive bundles (functionality). If both of the above options fail, application runtime 410 may temporarily disable low priority functionalities put constraints on number of simultaneous parallel threads executing in the application or modules running in it, shrink application threadpool size, disable or uninstall low priority modules, or serialize the execution of power-intensive tasks one after the other instead of letting them run concurrently. The application runtime 410 may also take converse action when power capping is revoked or the power management policy is favorable to performance.

In one embodiment, application engine 410 may perform combinations of the above according to user preferences in preferences data structure 413. That is, preferences data structure 413 may comprise preferences for power management with respect to provisioning and/or migrating application 411. Preferences 413 may specify whether application 411 must complete functions or services before changing power management profile. Preferences 413 may specify whether application runtime 410 may disable particular functions or services or whether application runtime 410 must disable particular functions or services when in power saving mode. Preferences 413 may also specify whether application runtime 410 is permitted to provision alternate modules in application 411 responsive to a change in power management policy. Preferences 413 may also specify whether application 410 is to revert back to the original configuration when changing from power saving mode to performance mode, for example.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in any one or more computer readable medium(s) having computer usable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CDROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in a baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Computer code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio frequency (RF), etc., or any suitable combination thereof.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java™, Smalltalk™, C++, or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the illustrative embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions that implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

FIGS. 5A and 5B present a flowchart illustrating operation of a mechanism for runtime based enforcement of energy policies in accordance with an illustrative embodiment. With reference to FIG. 5A, operation begins when provisioning an application in an application runtime (block 500), and the mechanism receives a notification of the power management policy from the virtual machine in which the application runtime executes (block 501). The mechanism requests power-specific application modules from a trusted module registry (block 502) and provisions the application modules (block 503).

The mechanism then determines whether the application runtime receives a notification indicating change in power management policy and determines whether power management policy calls for less power than, more power than, or the same power as the current power policy (block 504). The power management policy may call for more power if a power cap is being revoked, for example. The power management policy may call for less power if a power cap is being enforced or the execution environment is entering power saving mode, for example. The power management policy may call for the same power if there is no change in the power policy, for example.

If the mechanism receives a notification and determines the power is the same as the current power policy in block 504, then the application runtime does not modify the behavior of the application, and operation returns to block 504 to determine whether the application runtime receives a notification indicating change in power policy.

If the mechanism receives a notification and determines the power policy calls for more power consumption than the current power policy, the mechanism checks application module properties (block 505). The mechanism determines whether at least one application module is sensitive to changes in power policy (block 506). If the mechanism determines no application modules are sensitive to changes in power policy, then operation returns to block 504 to determine whether the application runtime receives a notification indicating change in power management policy.

If the mechanism determines at least one application module is sensitive to changes in power policy in block 506, then the mechanism determines whether to replace application modules with alternate, power-specific modules (block 507). The mechanism may determine to replace application modules based on preferences in a preferences data structure or based on whether such alternate modules are available. If the mechanism determines to replace one or more application modules, the mechanism requests power-specific application modules from a trusted module registry (block 508). The mechanism then provisions the alternate application modules (block 509).

Thereafter, or if the mechanism cannot or does not replace application modules in block 507, the mechanism determines whether to enable functions or services in the application (block 510). The mechanism may determine to re-enable functions or services that were previously disabled based on preferences in a preferences data structure or based on whether the mechanism was able to replace application modules with power-specific modules. If the mechanism determines to re-enable functions or services, the mechanism re-enables secure functions in the application modules (block 511). Thereafter, or if the mechanism determines to not enable functions or services in block 510, operation returns to block 504 to determine whether the application runtime receives a notification indicating change in power policy.

If the mechanism receives a notification and determines the power policy calls for less power than the current power policy in block 504, then turning to FIG. 5B, the mechanism determines whether to request delay of a power cap or power saving mode (block 512). If the mechanism determines to request delay of a power cap, the mechanism requests delay in enforcing the power cap or power saving mode (block 513). The mechanism completes critical processing (block 514). Then, the mechanism checks application module properties (block 515).

Thereafter, or if the mechanism does not request delay in enforcing the power cap or power saving mode in block 512, the mechanism determines whether at least one application module is sensitive to changes in power policy (block 516). If the mechanism determines no application modules are sensitive to changes in power policy, then operation returns to block 504 in FIG. 5A to determine whether the application runtime receives a notification indicating a change in power policy.

If the mechanism determines at least one application module is sensitive to changes in power policy in block 516, then the mechanism determines whether to replace application modules with alternate, power-specific modules (block 517). The mechanism may determine to replace application modules based on preferences in a preferences data structure or based on whether such alternate modules are available. If the mechanism determines to replace one or more application modules, the mechanism requests power-specific application modules from a trusted module registry (block 518). The mechanism then provisions the alternate application modules (block 519).

Thereafter, or if the mechanism cannot or does not replace application modules in block 517, the mechanism determines whether to disable functions or services in the application (block 520). The mechanism may determine to disable functions or services based on preferences in a preferences data structure or based on whether the mechanism was able to replace application modules with power-specific modules. If the mechanism determines to disable functions or services, the mechanism disables functions or services in the application modules, or otherwise modifies behavior of the application to be more power conservative (block 521). Thereafter, or if the mechanism determines to not disable functions or services in block 520, operation returns to block 504 in FIG. 5A to determine whether the application runtime receives a notification indicating change in power policy.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Thus, the illustrative embodiments provide mechanisms for runtime based enforcement of energy related policies between a host or virtual machine and an application runtime in a cloud computing environment. The application runtime based cloud application intelligently adapts its behavior based on the power management policies of the execution environment, which may change due to changes in the policies over time or due to changes in execution environment due to migration of the virtual machine and hence associated policies. The illustrative embodiments provide a provision for notifying the application runtime about execution environment power policies, changes in these policies, either due to higher-level policies, events in the cloud environment, or change in the host due to migration of the virtual machine. The illustrative embodiments also provide a provision for the application runtime to interact with the execution environment either the virtual machine or the host—to defer, with time duration as one input, enforcement of certain power management policies based on the workload or task currently being executed in the application. The illustrative embodiments also provide the ability of the application runtime to disable or enable a subset of functionality, request more services from the runtime, or seek specific implementations in response to changes in the execution environment power management policies.

As noted above, it should be appreciated that the illustrative embodiments may take the form of an entirety hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In one example embodiment, the mechanisms of the illustrative embodiments are implemented software or program code, which includes but is not limited to firmware, resident software, microcode, etc.

A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems and Ethernet cards are just a few of the currently available types of network adapters.

The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated. 

1. A method, in a data processing system, for runtime based enforcement of energy policies, the method comprising: receiving, by an application runtime environment executing within a virtual machine on the data processing system, notification of a change in energy policy for the virtual machine or a physical host on which the virtual machine is executing; and responsive to determining the virtual machine is to be run under a power cap based on the notification of a change in energy policy, dynamically modifying, by the application runtime environment, execution of an application in the application runtime environment, wherein the application comprises a set of application modules.
 2. The method of claim 1, wherein modifying execution of applications in the application runtime environment comprises disabling functionality of at least one application module within the set of application modules.
 3. The method of claim 1, wherein modifying execution of applications in the application runtime environment comprises disabling at least one module or service executing in the application runtime environment.
 4. The method of claim 1, wherein modifying execution of applications in the application runtime environment comprises: querying a service registry for a power-conservative alternate version of a software module; and deploying the alternate version of the software module in the application runtime environment.
 5. The method of claim 1, wherein each software module in the set of software modules has an attribute that indicates whether the software module is sensitive to power capping.
 6. The method of claim 5, wherein modifying execution of applications in the application runtime environment comprises: identifying a given software module in the set of software modules with an attribute indicating the given software module is sensitive to power capping; querying a service registry for an alternate version of the given software module, wherein the alternate version of the given software module has an attribute indicating the alternate version of the given software module is not sensitive to power capping; and deploying the alternate version of the given software module in place of the given software module.
 7. The method of claim 1, further comprising: responsive to determining the virtual machine is to be run under a power cap, requesting, by the application runtime environment, delay of the change in energy policy.
 8. The method of claim 1, wherein modifying execution of applications in the application runtime environment comprises one of placing constraints on a number of simultaneous parallel threads executing in the set of software modules, shrinking application threadpool size, or serializing execution of power-intensive tasks. 9-24. (canceled) 